Power mode aware packet communication method and apparatus

ABSTRACT

Packet communication method and system in which a packet destined for a terminal is provided service according to a service table indexed by packet classification and the terminal&#39;s power mode. The service table may specify for a connection a predetermined quality of service or discarding the packet. For a power mode having an alerting (i.e., paging) mechanism, the service may include alerting the terminal. The service table may also include a network edge point&#39;s own service requests and service requests from terminals, provisioning servers, and handoff sources. For a multicast or broadcast packet, as each terminal may be in a different power mode, the associated service in the service table may therefore be different for each terminal. In that case, the packet is provided with service so that any given terminal is provided with at least the quality of service specified in the service table. Thus, a multicast or broadcast packet is discarded when the service specified for all terminals is “discard.” Each terminal is alerted, however, if the associated service includes alerting the terminal. During handoff, a part of service table associated with the terminal can be transferred from the handoff source to the handoff destination.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application relates to, and claims priority of, (a) U.S.provisional patent application, entitled “Power Mode Aware PacketCommunication Method and Apparatus,” Ser. No. 60/581,683, filed on Jun.22, 2004, (b) U.S. provisional patent application, entitled “Power ModeAware Packet Communication Method and Apparatus,” Ser. No. 60/601,411,filed on Aug. 13, 2004 and (c) U.S. provisional patent application,entitled “Power Mode Aware Packet Communication Method and Apparatus,”Ser. No. 60/605,044. filed on Aug. 27, 2004.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to protocols in a data network. Inparticular, the present invention relates to protocols used amongnetwork access device and terminals having power saving states.

2. Discussion of the Related Art

Many communication devices provide “normal” or “active” mode and“power-saving” modes of operation. Normal or active mode typicallyrefers to the device's highest performance mode of operation, in whichalso is typically the mode with the highest power consumption. Apower-saving mode, by contrast, is a mode of operation in whichperformance is traded off for a lower level of power consumption.Multiple modes of operations with different levels of performance andpower consumption are found in most computers and communication devicestoday. For example, battery-powered devices in wireless communicationsystems, such as IEEE 802.11 WLAN (Wireless Local Area Network), IEEE802.16 Wireless MAN (Metropolitan Area Network), GSM, IS-95, W-CDMA,CDMA 2000, all provide active and power-saving modes of operation. Inparticular, an IEEE 802.11 device has two power modes: an active (i.e.,normal operation) and a power-saving mode. Under a power-saving mode,the device shuts off a part of its circuitry. Similarly, an IEEE 802.16device has three power modes (“normal,” “sleep,” and “idle” modes), eachmode having a prescribed level of communication and power-savingcapabilities.

Under most conventional power-saving modes, a wireless terminal can bealerted (or paged). Typically, an alerted wireless terminal returns toan active mode of operation to process the packets which have arrivedsince the terminal entered the power-saving mode.

Some conventional power-saving modes trade-off power consumption andcommunication capabilities. However, in a conventional power-savingmode, a wireless terminal does not control whether or not packetsarriving during a power-saving mode are to be delivered or discarded.For example, under the IEEE 802.11 standard, packets are buffered forlater delivery. Under the latest IEEE 802.16 standard at the earliestpriority date of this application, however, the packets are eitherdiscarded or delivered according to system settings. In addition, aconventional power-saving mode provides a wireless terminal littlecontrol over the alert mechanism. Generally, when a packet arrives at atime when the wireless terminal is in a power-saving mode, the wirelessterminal is alerted. Efficiency suffers because a terminal lacks controlof both packet disposition and the alert mechanism during a power-savingmode.

In a communication network, at times, some packets are of littleinterest to a wireless terminal. For example, a “Voice over IP” (VOIP)enabled wireless terminal running under the Windows CE operating systemmay discard all broadcast AppleTalk or IPX packets received. The samewireless terminal, however, may receive NetBIOS packets for file andprinter sharing and Session Initiation Protocol (SIP) packets forinitiating a VoIP session. Because the wireless terminal does notcontrol packet disposition upstream, even packets of no interest aredelivered. However, if the rule is for discarding all packets arrivingduring a power-saving mode, the performance of a desired service mightdeteriorate significantly, as its packets are also discarded.

Further, because the terminal lacks control over the alert mechanism,the terminal is alerted by any packet that arrives during a power-savingmode. Clearly, such an alert policy wastes power on undesired packets.In a real computer and communication network, different packet handlingmethods are required under different power-saving operations. Forexample, in a VoIP enabled wireless terminal running the Windows CEoperating system, while both NetBIOS and SIP packets are relevant in onepower mode (e.g. sleep mode in IEEE 802.16), only SIP packets arereceived in another power mode (e.g. idle mode in IEEE 802.16) tofurther conserve power.

In some applications, “classification” may be used to determinedisposition of a packet. For example, packets may be classifiedaccording to source and destination addresses, port numbers and aprotocol identifier. In some applications, disposition of a packet maybe a decision based on both the identity of the wireless terminal (e.g.,its MAC or IP address) and the port number. One example of such anapplication is a network firewall providing packet blocking services fora security purpose (e.g., to prevent unauthorized access). FIG. 1 is ablock diagram showing conventional network firewall 100, includingpacket classifier 101 under direction of a filter table in filtermanager 103. Packets classified to be acceptable are passed to theirspecific recipients, and packets deemed unacceptable are passed todropper 102 to discard. Table 1 is an example of a filter table suitablefor use in network firewall 100. In network firewall 100, packets areprocessed without regard to the recipients' power modes.

TABLE 1 Network Firewall Filter Table (Prior Art) Classifier SRC DST SRCADDR DST ADDR Port Post Protocol Lifetime Action Any 82.48.42.112 Any 21TCP 0 Deny Any 82.48.42.112 80 Any TCP 1 Allow 82.48.42.112 Any 137 137UDP Default Deny

In a communication system, “quality of Service” (QoS) capability (e.g.,IEEE 802.16) is typically provided to each connection according to a QoStable based on packet classification. Table 2 is an example of a QoStable. FIG. 2 is a block diagram of conventional QoS enabledcommunication system 200, which includes classifier 201 and QoSmechanism 202. In QoS enabled communication system 200, multipleconnections are maintained by connection manager 203. In this example,packets may be classified according to source and destination addresses,source and destination ports, protocol and connection identity (ID)information. According to their classifications, appropriate QoS actionsare taken on the packets based on the QoS table. In communication system200, a packet is also processed without regard to the recipients' powermodes.

TABLE 2 Connection-Based QoS Table (Prior Art) Classifier Connec- SRCDST Pro- tion SRC ADDR DST ADDR Port Port tocol ID Action 82.68.42.5682.48.42.112 80 3900 TCP 1 QoS spec 1 82.68.42.56 82.48.42.112 Any 5004UDP 2 QoS spec 2 Any 82.48.42.113 139 139 TCP 1 QoS spec 3

A packet communication method is desired in which each packet isprocessed according to the packet's classification and the power mode ofits recipient. Further, it is also desired of such a packetcommunication network to determine whether or not to alert a recipientin a power-saving mode.

SUMMARY

The present invention provides both a method and an apparatus for packetcommunication in which a packet is processed according to a servicetable indexed by a packet's classification and each receiving terminal'spower mode. The service may specify, for example, whether the packet isto be provided a predetermined quality of service or to be discardedbased on the receiving terminal's power mode. The service may alsospecify whether a receiving terminal is to be alerted or paged. Theservices specified in the service table may pertain, for example, to aterminal, a provisioning server, or a handoff source. At the time when amulticast or broadcast packet is received, different receiving terminalsmay be in different power modes and thus, the service table may specifydifferent services for the different terminals according to theirrespective power modes. The service table ensures that a terminal isprovided at least the level of service indicated in the service table.As a result, a multicast or a broadcast packet is discarded only whenthe service table instructs discarding the packet for all terminals. Theservice table may also specify whether or not a terminal is to bealerted under each power state of a terminal. When a terminal makes ahandoff between network access points, a part of the service tableassociated with the terminal may be transferred from the handoff sourceto the handoff destination.

The invention provides another way to trade-off between power saving andcommunication capability. By discarding less important packets andpreventing the packets from triggering alerts (I,e., pages) to thewireless terminals, efficiency of existing power-saving modes can befurther improved.

The above trade-off can be made in a flexible way based on thefunctionality of packet and the power mode of the terminals. Even whenthe packet is multicast or broadcast, such a flexible trade-off ispossible for each receiving wireless terminal.

In one embodiment, the procedures for packet filters, load activationand QoS connection setup can be integrated into one.

The present invention enables fast and low overhead slaved activation ofQoS and packet filtering mechanisms during power mode changes.Procedures for entering into and exiting from power saving modes can beused to trigger the activation or deactivation of QoS and packetfiltering associated with the power mode. Consequently, fast activationand deactivation are achieved without additional separate signaling.

The present invention allows a low overhead and power efficientprocedure for relocating a service table relevant to a new networkattachment point during a wireless terminal handoff. By transferring thepart of a service table associated with the wireless terminal from acurrent network edge point to another network edge point, a new servicetable is set up at the new network edge point with minimal signaling,thereby achieving low overhead and power efficiency.

The present invention also allows a low overhead procedure for retainingresources of terminals in power saving modes without sacrificingperformance. This is achieved using a combination of slaved connectiontermination techniques and by providing resource retaining fields andpower mode transition rules in control messages and connectionestablishment or change message.

The invention is achieved with minimal or no modification of existinghardware, using procedures that are analogous to those used for Qualityof Service (QoS) functions and packet filtering. Thus, the presentinvention may be achieved with minimal implementation costs andoperation overheads. The packet classification hardware and the memoryallocated to service tables, classification rule tables, service ruletables, and alerting rule tables can be shared.

The present invention is better understood upon consideration of thedetailed description below and the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing conventional network firewall 100having filter manager 103, which operates in conjunction with packetclassifier 101 and packet dropper 102.

FIG. 2 is a block diagram of conventional QoS enabled communicationsystem 200, which includes classifier 201 and QoS mechanism 202 forproviding QoS services according to a service table.

FIG. 3 shows communication system 300, which includes network 301 havingnetwork edge points or access points 302 and 303.

FIG. 4 is a functional block diagram of network edge point 400 inaccording with one embodiment of the present invention.

FIG. 5 is a functional block diagram of terminal 500 according to thepresent invention.

FIG. 6 shows a provisioning process, in accordance with one embodimentof the present invention.

FIG. 7 shows a handoff procedure by which a terminal detaches from onenetwork edge point and attaches to another.

FIG. 8 shows flow chart 800, illustrating exemplary packet processprocedures 801-805 at an network edge point.

FIG. 9 illustrates a connection setup procedure, in which a terminalsends a connection setup request message.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The invention provides a power mode aware packet communication system,which avoids delivering undesired packets or alerting wireless terminalsunnecessarily, thereby saving power. The present invention is applicableto a communication system, such as communication system 300 of FIG. 3,which includes network 301. As shown in FIG. 3, network 301 isaccessible through network edge points or access points 302 and 303.FIG. 3 also shows network device 307, which is directly attached tonetwork 301, and terminals 304, 305 and 306, which are connected tonetwork 301 through network edge points 302 and 303. Network 301 may bea global network, such as the Internet, a metropolitan area network(MAN), a wide area network (WAN), or a local area network (LAN).Alternatively, network 301 may include also a core network, a backbonenetwork, a backhaul network, or an access network. The present inventionis applicable to communication between terminals coupled to the samenetwork edge point (e.g., terminals 305 and 306 connected to networkedge point 302), or between any two or more terminals coupled to thenetwork 301 in any way. The communication may be associated with inboundpackets (i.e., going from a terminal to a network edge point), outboundpackets (i.e., going from a network edge point to a terminal), or both.

Network edge points 302 and 303 each may be an access point under theIEEE 802.11 standard, a base station under any of the IEEE 802.16, GSM,IS-95, W-CDMA and CDMA 2000 standards, a hub in IEEE 802.3 Ethernetnetwork, a point-to-point protocol (PPP) server of an internet serviceprovider (ISP), a business enterprise or other dial-up network, or anynetworked edge point of LANs, WANs, MANs, satellite networks, Bluetoothnetworks or any other type of networks.

FIG. 4 is a functional block diagram of network edge point 400 inaccordance with one embodiment of the present invention. As shown inFIG. 4, network edge point 400 includes classifier 401, connectionmanager 402, power mode manager 403, service manager 404, QoS mechanism407, dropper 408, provision manager 405, and handoff manager 406.Although not expressly shown in FIG. 4, other functional blocks may alsobe provided in network edge point 400. Connection manager 402 maycommunicate with a counterpart connection manager in a terminal (e.g.,connection manager 501 of FIG. 5), provision manager 405, and handoffmanager 503 to setup, change, and terminate a connection, respectively.

In this embodiment, terminals 304, 305, 306 and 307 each may be adesktop computer, a server, a laptop computer, a personal digitalassistant (PDA), a pocket PC, a wireless telephone, a cellular phone, asmart phone, a data card, a PCMCIA card, an USB stick, or anothercommunications enabled chip or device. Each of terminals 304, 305, 306and 307 may be configured as a client, as a server, or as a peer (forpeer-to-peer communications). Communication may be conducted, forexample, over wireless communication. Further, each terminal may bebattery-powered.

FIG. 5 is a functional block diagram of terminal 500 according to thepresent invention. As shown in FIG. 5, terminal 500 may includeconnection manager 501, power mode manager 502, handoff manager 503 andany other functional blocks useful for packet communication. Connectionmanager 501 communicates with its counterpart in a network edge point(e.g., connection manager 402 of network edge point 400) regardingclassification rules, service tables, service rules, and paging rules,as appropriate. Similarly, power mode manager 502 may communicate itspower mode to its counterpart in a network edge point (e.g., power modemanager 403 of network edge point 400). Power mode manager 502determines a suitable power mode for terminal 500, based on, forexample, the operating system, installed and running services orapplications, the current power mode or the battery status. Whenever apower mode is changed, power mode manager 502 communicates the powermode change to connection manager 501.

FIG. 8 shows flow chart 800, illustrating an exemplary packet processingprocedure at a network edge point, such as network edge point 303 ofFIG. 3. Flow chart 800 includes steps 801-805. At step 801, when anoutbound packet designating a terminal is received from network 301 orreceived at a network edge point (e.g., network edge point 302),classifier 401 classifies the received packet according to an applicableclassification rule installed by connection manager 402. For example,classifier 401 may classify packets according to a “connection”identifier, which also identifies one or more receiving terminals (step802). At step 803, the power mode of each receiving terminal may bedetermined by power mode manager 403. At step 804, the classified packetis provided to service manager 404 which determines the processingrequirement of the packet (i.e., the specified action) from a servicetable installed by connection manager 402. The processing requirementmay be, for example, delivering the packet to QoS mechanism 407, ordiscarding the packet in dropper 408. The specified action may bedetermined from the service table, for example, from the packet'sclassification and the power mode of each receiving terminal. Thespecified action is performed at step 805. In addition, the servicetable may also specify whether a receiving terminal in a power-savingmode should be alerted, according to an alerting rule. Examples ofalerting mechanisms include paging schemes under IS-95, CDMA-2000, GSM,W-CDMA, or other cellular systems, traffic indication scheme under IEEE802.11, paging schemes and traffic indication schemes under IEEE 802.16.

The present invention is applicable to a wide variety of packets atvarious protocol layers, such as Medium Access Control (MAC) layerframe, Logical Link Control (LLC) frame, Internet Protocol (IP) packet,Asynchronous Transfer Mode (ATM) cell, datagram, or any other type ofnetwork message under a packet-based protocol. The present invention maybe applicable to (a) network messages for specific services, such asvoice over IP (VoIP), video teleconferencing, text messaging, filesharing, video streaming, audio streaming, web browsing, shortmessaging, multimedia broadcasting or multicasting, e-mail, or anothercommunication format; (b) network messages for specific operatingsystems (OS), such as NetWare, AppleTalk, UNIX, Windows, or Windows CE;(c) network messages for internetwork packet exchange (IPX), sequencedpacket exchange (SPX), routing information protocol (RIP), NetWare linkservices protocol (NLSP), network basic input/output system (NetBIOS),NetBIOS extended user interface (NetBEUI), EtherTalk link accessprotocol (ELAP), LocalTalk Link Access Protocol (LLAP), TokenTalk LinkAccess Protocol (TLAP), or datagram delivery protocol (DDP); and (d)network messages for transmission control protocol (TCP), user datagramprotocol (UDP), session initiation protocol (SIP), trivial file transferprotocol (TFTP), file transfer protocol (FTP), real time protocolg(RTP), hypertext transfer protocol (HTTP), DHCP (Dynamic HostConfiguration Protocol) discovery, DHCP request, agent advertisements,router advertisements, neighbor discovery, multicast listener discovery(MLD), internet group management protocol (IGMP), or any kinds ofinternet control message protocol (ICMP). The packet may include controlmessages, management messages, or data messages. Table 3 is an exemplarymessage format that may be used for communication between a network edgepoint and a terminal, or between the two network edge points. As shownin Table 3, the message format may indicate a destination (DST) and asource (SRC), which may be specified as an IP address, a MAC address, anLLC address, or any other address or identifier that identifies thedestination and the source of the message. The packets may be unicast,multicast, or broadcast.

TABLE 3 Message format DST SRC CMD

In Table, 3, an additional field provides a coded or uncoded command(CMD). Some examples of applicable commands are provided in Table 4. Amessage may be piggybacked by one or more other data messages, controlmessages, management messages, or any other network messages. Eachmessage may include more than one CMD.

TABLE 4 Commands CMD Message 1 Connection setup request 2 Connectionsetup response 3 Connection setup ACK 4 Connection change request 5Connection change response 6 Connection change ACK 7 Connection closerequest 8 Connection close response 9 Sleep mode request 10 Sleep moderesponse 11 Traffic indication 12 Idle mode request 13 Idle moderesponse 14 Paging 15 Handoff request 16 Handoff response 17 Connectiontransfer request 18 Connection transfer response 19 Connection transferACK

A terminal may specify the type of packets that it wished to receive, byspecifying the packets' source and destination addresses, its operatingsystem (OS), its installed or running services or applications, itscurrent power mode, its battery status, or any other state information.According to the present invention, a network edge point may discardundesired packets without alerting the terminal, thus achieving powersaving.

Under an active or normal mode operation (e.g., an active mode underIEEE 802.11, a normal mode under IEEE 802.16, an access state or trafficchannel state under IS-95, a system access state under CDMA-2000, or adedicated mode under GSM), a terminal may be more tightly coupled to thenetwork, transmitting or receiving packets, preparing to transmit orreceive a packet, or carrying out other communication processes. Manylevels of power saving modes may be provided. Typical power-saving modesmay include sleep, dormant, idle, standby, or hibernated modes. Under apower-saving mode (e.g., a power-saving mode under IEEE 802.11, an idlemode or a sleep mode under IEEE 802.16, an idle state or mode underIS-95, CDMA-2000, or GSM), a terminal may be relatively more looselycoupled to the network, with restrictions imposed upon its operations,including its network communications. A terminal in a power-saving modemay be restricted to receiving or transmitting only specific types ofpackets, within specific time or slots, using specific channels, orunder other operational constraints. Such restrictions allow a terminalin a power-saving mode to cut off power from circuits not necessary forproviding the restricted capabilities.

A terminal in a power-saving mode may still select or reselect networkedge points, or transfer channels (e.g., paging or quick pagingchannels, common signaling channels) it monitors from one network edgepoint to another, for example. In some applications, the monitoredchannels transmit only during specified time slots which occurperiodically, pseudo-periodically, or aperiodically according topredetermined rules. The monitored channel may include beacon frameswhich may be transmitted by network edge points periodically,pseudo-periodically, or aperiodically. Alternatively, the monitoredchannels may be defined by a set of codes, a set of sub-channels, a setof sub-carriers, a set of frequency hopping patterns. The terminal mayhave registered on the network and may be listening for a predeterminedmessage (e.g., an alerting message, a paging message, a trafficindication message). The terminal may perform location updates whennecessary.

According to one embodiment of the present invention, when a terminalchanges its power mode, the terminal and a network edge point with whichthe terminal associates exchange power mode transition messages. In oneimplementation, the messages exchanged may include, for each transitiontype, a “request for power mode transition,” and a response to therequest. The request message may be initiated by either the terminal orthe network edge point, and the response message is sent by the partyreceiving the request message. Table 4 above includes examples of thesepower mode transition messages (e.g., a sleep mode request, a sleep moderesponse, an idle mode request, and an idle mode response). As withother messages, the power mode transition message may be piggybacked byother network messages. Alternatively, the power mode transition messagemay also be implicit. For example, a network message that relates to anoperation performed only in a power mode different from the currentpower mode of the terminal may be treated as including implicitly apower mode transition message, so as to allow the terminal to enter thepower mode in which the operation may be performed. For example, in apacket communication system having a normal mode, a sleep mode, and anidle mode, a data message sent by a terminal in a sleep mode or idlemode, and an ACK message sent by a network edge point may be treating asincluding, respectively, a power mode transition request for exiting thesleep mode or the idle mode, and a corresponding response.

A power mode transition message may also include a resource retentionfield (RSC RTN), such as shown in Table 5. Such a power mode transitionmessage is a variation of the messages of Table 3 above. Exemplaryvalues for the RSC RTN field are shown in Table 6. The resourceretention field may specify a request, a response, a preference, acommand, or a policy by a terminal or a network edge point regarding thetreatment of resources allocated at the network edge point to theterminal for the duration within which the terminal is in the specifiedpower mode. The value in the resource retention field may be interpretedas a request for the retaining the associated resource for the terminal.

TABLE 5 Power mode transition message (resource retention field) DST SRCCMD RSC RTN

TABLE 6 Resource retention field Field value Resource retaining behavior1 No resource for any connections are retained 2 Only the resource forconnection(s) with the predetermined connection type(s) is retained 3Only the resource for connection(s) with the resource retaining rule of“To retain” is maintained 4 Only the resource for connection(s) with thealerting rule of “To alert” is maintained . . . . . . N Resource of allconnections is maintained

As shown in Table 6, a value ‘1’ at the resource retention field istreated as a request that the resources for all connections are to bereleased. The network edge point would free up all resources for theterminal (i.e., all entries and resources in service table, alertingrule table, classification rule table, service rule table, classifier,scheduler, poller, politer, shaper, buffer, bandwidth allocation unit,and resource reservation unit), when the terminal transitions to apower-saving mode. Of course, under such a resource retention policy, aterminal may suffer from QoS degradation, undesirable packet blocking,undesirable packet delivery, undesirable alerting, and undesirable lackof alerting. Another example corresponds to the case in which theresource retention field is ‘N’. As shown in Table 6, under thatresource retention policy, all resources are to be retained. Byretaining all resources, a terminal may enjoy better QoS, and therecovery from a power-saving mode to normal mode may be faster andsmoother. However, the burden on the network edge point iscorrespondingly higher.

As yet another example, corresponding to a value of ‘2’ in theresource-retention field, resources are retained only for specifiedtypes of connections. Which connection types merit resource retentionare determined by weighing the overhead costs of resource retentionagainst the attendant benefits, considering such factors as thefunctions performed by the connection types, the QoS required for theconnection types, the associated overhead costs of resource retention,and the total available resources at the network edge point. Forexample, a network edge point of a packet communication system mayretain resources for basic, primary management and secondary managementconnections after considering the factors enumerated above.

In Table 6, the cases corresponding to values ‘3’ and ‘4’ representretention policies in which resources are retained only by specificrequests or as required by an alert rule. Because these policies involveevaluations involving factors in addition to merely connection types, agreater range of flexibility and finer control for greater power-savingare made possible.

Referring back to FIG. 4, power mode manager 403 of network edge point400 may send an alerting message to terminal 500. Tables 7 and 8 showthe formats of a traffic indication message and a paging message,respectively. The message formats in Tables 7 and 8 are variations tothe message format of Table 3. As these alerting messages may bebroadcast or multicast, the receiving terminals may be specifiedseparately from the destination address (DST). For example, theterminals may be specified in the traffic indication field or the paginginfo field of the messages shown in Tables 7 and 8.

TABLE 7 Traffic indication message DST SRC CMD Traffic indication

TABLE 8 Paging message DST SRC CMD Paging info

An alerting message from a network edge point may convey informationregarding pending packets for the terminal. Alternatively, the alertingmessage may be a request to the terminal for performing operations suchas ranging, scanning, location update, acknowledgement, idle handoff,handoff, or a request for changing the power mode. The information orrequest in an alerting message may be interpreted by a power modemanager of the terminal (e.g., power mode manager 502 of terminal 500).Upon receiving the message, the terminal may initiate the requiredoperation, to receive the pending packets or to respond to the request,as appropriate.

According to one embodiment of the present invention, a power modemanager (e.g., power mode manager 403 of network edge point 400)maintains an alert rule table to determine if an alerting message shouldbe sent to a receiving terminal, according to packet classification, theidentity of the receiving terminal, and the terminal's power mode. Oneexample of an alerting rule table is shown in Table 9 below.

TABLE 9 Alerting Rule Table Connection ID Receiver ID Power status Alert1 1 Sleep O Idle X 2 1 Sleep X Idle X . . . . . . . . . . . . I 2 SleepO Idle X i + 1 1 Sleep X Idle X 2 Sleep O Idle X . . . . . . . . . NSleep X Idle X . . . . . . . . . . . . M N Sleep O Idle O

As shown in Table 9, when a packet designating connection ID ‘1’ andreceiver ID ‘1’ is received while the receiving terminal is in sleepmode, an alerting message is sent to the receiving terminal. Similarly,as shown in Table 9, a packet designating connection ID ‘2’ and receiverID ‘1’ would not trigger an alerting message, regardless of whether thereceiving terminal is in sleep mode or idle mode.

A power mode manager of a network edge point (e.g., power mode manager403) may maintain a terminal power status table (e.g., Table 10), whichstores a current power mode for each associated terminals. The terminalpower status table is updated when a power mode of a terminal ischanged. Through the power mode manager, the terminal power status tablemay be accessed by other functional blocks of the network edge point,such as a service manager (e.g., service manager 404), or a QoSmechanism (e.g., QoS mechanism 407).

TABLE 10 Terminal Power status table Terminal ID Power status 1 Normal 2Sleep . . . . . . N Idle

The power mode manager of a network edge point may maintain an alertingrule table, such as Table 9, so as to provide an alerting messageservice. Alternatively, the alert rule table may be incorporated into aservice table under control of a connection manager (e.g., connectionmanager 402) of the network edge point. In that case, upon receiving apacket from the network, the power mode manager of the network edgepoint communicates with the connection manager to access the servicetable.

In this detailed description, the term ‘connection’ refers to a group ofdata packets that flow between a network edge point and a terminal whichare associated with a particular service. For example, a connection mayrepresent a virtual channel or a virtual path in ATM, a traffic streamor a traffic flow in IEEE 802.11e, a connection or a service flow inIEEE 802.16, a connection, a session, a flow, or a service in GSM,W-CDMA, IS-95, W-CDMA, IETF integrated service (Int-Serv). In this senseof the word, a connection may encompass data traffic both under aconnection-oriented protocol and a connectionless protocol (e.g.,Internet Protocol (IP)). Multiple virtual paths, virtual channels,traffic streams, traffic flows, connections, service flows, sessions, orflows may be served by a single connection. Conversely, a virtual path,a virtual channel, a traffic stream, a traffic flow, a connection, aservice flow, a session, or a flow may be served by multipleconnections. In one embodiment, a connection may be identified by packetclassification, and may be associated with a “connection identifier”(CID). As discussed above, a classifier is a set of matching criteriaapplied to a packet. The matching criteria may be protocol-specificpacket attributes (e.g., destination IP address). Examples ofconnections grouped by classification are shown in Tables 11 and 12.Each connection in Table 12 is explicitly associated with a CID. Tables11 and 12 illustrate classifications based on source MAC address (SRCMAC ADDR), destination MAC address (DST MAC ADDR), frame type (FRMType), source IP address (SRC IP ADDR), destination IP address (DST IPADDR), source port (SRC Port), destination port (DST Port), and protocolfiled (Protocol).

Although not shown in Table 11 (to simplify this description), analerting rule may also be provided for each connection.

Packet classification may be based on an ATM header, a MAC header, anLLC header, an IP header, a TCP header, a UDP header, or any otherheader, body, trailer, or any other part of a data packet. For example,in an ATM connection—which is uniquely identified by the values of avirtual path identifier (VPI) and a virtual channel identifier(VCI)—packet classification may be based on the VPI and VCI fields inthe ATM cell header. As another example, for an IEEE 802.3 packet,packet classification can be based on the destination MAC address,source MAC address, and Ethertype/SAP fields. For an IP packet, forexample, packet classification may be based on the Type of Servicefield, Protocol field, IP source address, IP destination address, sourceport, and destination port. Packet classification may be based on maskedor unmasked fields.

TABLE 11 Service table in a network edge point Classifier Power Mode SRCDST Conditioner MAC MAC FRM SRC IP DST IP SRC DST Pro- RCV Power ADDRADDR Type ADDR ADDR Port Port tocol ID status Action Any Any IP82.68.42.56 82.48.42.112 80 3900 TCP 1 Normal QoS spec 1 Sleep QoS spec2 Idle Discard Any Any IP 82.68.42.56 82.48.42.112 Any 5004 UDP 1 NormalQos spec 3 Sleep Discard Idle Discard . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . Any Any IP Any 82.48.42.113 139 139 TCP2 Normal QoS spec j Sleep QoS spec k Idle Discard Any Broad IP Any Any138 138 UDP 1 Normal QoS spec 1 cast Sleep Discard Idle Discard 2 NormalQoS spec 1 Sleep QoS spec 2 Idle Discard . . . . . . N Normal DiscardSleep Discard Idle Discard . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . Any Any IP Any 82.48.42.14 Any 5060 UDP N Normal QoSspec 1 Sleep QoS spec 2 Idle QoS spec 4

TABLE 12 Classification rule table Classifier SRC DST MAC MAC Frame SRCIP DST IP SRC DST ADDR ADDR Type ADDR ADDR Port Port Protocol CID AnyAny IP 82.68.42.56 82.48.42.112 80 3900 TCP 1 Any Any IP 82.68.42.5682.48.42.112 Any 5004 UDP 2 . . . . . . . . . . . . . . . . . . . . . .. . . . . Any Any IP Any 82.48.42.113 139 139 TCP i Any Broadcast IP AnyAny 138 138 UDP i + 1 . . . . . . . . . . . . . . . . . . . . . . . . .. . Any Any IP Any 82.48.42.14 Any 5060 UDP N

Several classifiers may exist for the same data service. Thus, aclassifier ordering scheme may be used in applying the classifiers tothe packets. An explicit ordering may be necessary where the patternsused by the classifiers may overlap. An ordering scheme need not beunique, but should unambiguously select the applicable classifier. Toprocess a packet, a classifier in a network edge point (e.g., classifier401 of network edge point 400) accesses a classification rule in aservice table (e.g., Table 11) through a connection manager (e.g.,connection manager 402). Alternatively, a classifier may maintain itsown classification rule table (e.g., Table 12), in which case, theclassifier is informed of changes impacting the classification ruletable by the connection manager (e.g., connection manager 402).

Table 13 is an example of a service table maintained by a connectionmanager of a terminal (e.g., connection manager 501 of terminal 500). Asshown in Table 13, the service table includes a classification rule anda service rule. Although not shown in Table 13 (to simplify thisdescription), an alerting rule may also be provided for each connection.

TABLE 13 Service table in a terminal (Receiver ID: 1) Classifier SRC DSTPower Mode MAC MAC FRM SRC IP DST IP SRC DST Conditioner ADDR ADDR TypeADDR ADDR Port Port Protocol (Power status) Action Any Any IP82.68.42.56 82.48.42.112 80 3900 TCP Normal QoS spec 1 Sleep QoS spec 2Idle Discard Any Any IP 82.68.42.56 82.48.42.112 Any 5004 UDP Normal QoSspec 3 Sleep Discard Idle Discard . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . Any Broadcast IP Any Any 138 138 UDP Normal QoSspec 1 Sleep Discard Idle Discard

The service tables of each terminal associated with a network edge pointare communicated to the network edge point through connection setup andchange procedures, as explained in further detail below. These servicetables are incorporated into the service table of the network edge point(e.g., the service table of in Table 11).

To setup, change, or terminate a connection, the respective connectionmanagers of a terminal and a network edge point exchange “connectionmanagement messages”. The connection management message may include aconnection setup request message, a connection setup response message,and a connection setup ACK message, as shown in Table 4. Tables 14, 15and 16 show exemplary formats of a connection setup request, connectionsetup response, and connection setup ACK messages for normal, sleep, andidle power modes, respectively.

TABLE 14 Connection setup request message DST SRC CMD Classifier NormalSleep mode Idle mode mode action action action

TABLE 15 Connection setup response message DST SRC CMD Classifier NormalSleep Idle mode Connec- mode mode action tion ID action action

TABLE 16 Connection setup ACK message DST SRC CMD Connection ID

FIG. 9 illustrates a connection setup procedure, in which a terminalsends a connection setup request message (step 901), such as that shownin Table 14. In response, the network edge point responds by sending aconnection setup response message (step 902). The terminal thenacknowledges receipt of the connection setup response message by sendingthe network edge point a connection setup ACK message (step 903).

The connection setup request message may specify, for example, thenetwork edge point's address in the DST field, the terminal's address inthe SRC field, a value ‘1’ in the CMD field, and the classification rulefor the connection in the Classifier field. As shown in Table 14, themessage may also include an action field for specifying a coded oruncoded service rule for each of the normal, sleep and idle power modes.For example, the service rule may be ‘to discard the packet’, ‘todeliver the packet’, ‘to deliver with a particular QoS specification’.When the service rule is coded, it may be coded as a TLV value (i.e.,type, length, and variable).

TABLE 17 Connection setup request message (QoS spec) AD AD 1 Classifier1 QoS spec 1 QoS spec 2 Discard NE TE

Table 17 shows an exemplary instance of a connection setup requestmessage. As shown in Table 17, this connection setup request messagespecifies for the normal, sleep and idle modes the service rules of ‘QoSspec 1’ delivery, ‘QoS spec 2’ delivery, and ‘discard,’ respectively.The addresses for the network edge point (AD NE) and the terminal (ADTE) are provided in the DST and SRC fields, respectively. Table 17illustrates a system which alerts a terminal only when a packet isdelivered. Under such a system, alerting rules need not be expresslyprovided in a connection setup request message. However, if a moresophisticated alerting mechanism is associated with the power modes, thealerting rules may be included in the respective action fields, as shownin the exemplary connection setup request message of Table 18. As shownin Table 18, ‘alert’ and ‘not to alert’ are specified for the sleep andidle modes, respectively. The alerting rule may be provided as a booleanvalue (i.e., complementary logic values for ‘alert’ and ‘not to alert.’)

TABLE 18 Connection setup request message (QoS spec & alert) AD AD 1Classifier 1 QoS spec 1 QoS spec 2 Discard NE TE Alert O Alert X

In one embodiment, a default service rule is provided for each powermode. For example, the default service rule for the sleep mode may be‘QoS spec 2’, while the default service rule for the idle mode may be‘discard’. With default service rules, the service rule for such a powermode need not be explicitly included in the power setup request message.Table 19 is an exemplary connection setup request message whichspecifies expressly the alerting rules for the sleep and idle modes, butallows the service rules for these power modes to be specifiedimplicitly.

TABLE 19 Connection setup request message (Alert) AD AD 1 Classifier 1QoS spec 1 Alert O Alert X NE TE

In one embodiment, a default QoS specification (e.g., ‘QoS spec 2’) isprovided for a particular power mode (e.g., sleep mode). A boolean valuemay then be used in the action field (i.e., complementary logic valuesfor ‘deliver’ and ‘discard.’), such as shown in Table 20.

TABLE 20 Connection setup request message (Deliver/discard & alert) ADAD 1 Classifier 1 QoS spec 1 Deliver Discard NE TE Alert O Alert X

If a system has both a default service rule and a default alerting rulefor each power mode, a connection setup request message need not specifyan action for each power mode. Table 21 shows a connection setup requestthat assumes a default service rule (e.g., ‘deliver packet’) and adefault alert rule (e.g., ‘alert’) for the sleep mode.

TABLE 21 Connection setup request message (Default Sleep mode) DST SRCCMD Classifier Normal Idle mode mode action action

As mentioned above, Table 15 shows an exemplary format for a connectionresponse message that responds to a corresponding connection setuprequest message. When a terminal initiates the connection setupprocedure, as shown in step 901 of FIG. 9, the connection setup responsemessage specifies the network edge point's address in the SRC field, theterminal's address in the DST field, and a value ‘2’ in the CMD field.The connection setup response message can have a classifier field, andaction fields for each of the normal, sleep and idle power modes. Theclassifier and action fields enable negotiation over the values of thesefields between the network edge point and the terminal. For example, thenetwork edge point may propose a downgraded QoS specification as theservice rule for the normal mode when the network edge point does nothave enough resources to support the QoS requested by the terminal. Ifsuch a negotiation is not required, a connection setup response messagemay simply include a boolean value indicating whether or not the networkedge point accepts classifier and actions specified in the terminal'sconnection setup request message. The network edge point may specify avalue in a connection ID (CID) field to identify the correspondingconnection between the network edge point and the terminal, which may beused in subsequent messages concerning this connection. (The CID fieldwould be included in a connection setup request message by the networkedge point.) Note that, the value in the CID field in the connectionsetup messages need not be what is used internally for connection IDused in the network edge point.

When a terminal sends the connection setup ACK message, the messagespecifies the network edge point's address in the DST field, theterminal's address in the SRC field, and a value ‘3’ in the CMD field.

If a power saving mode is associated with a slaved connectiontermination (i.e., a connection termination that is triggered by aspecified event, such as a power mode transition), the connection setuprequest need not include an action field for each power mode. Forexample, if the idle mode is associated with a slaved connectiontermination, the connection setup request message need not provide anaction field for the idle mode, as shown in Table 22.

TABLE 22 Connection setup request message (Slaved termination for idlemode) DST SRC CMD Classifier Normal Sleep mode mode action action

Where a power saving mode is associated with a slaved connectiontermination, a terminal or a network edge point may request that aspecified connection be excluded from the slaved connection termination.The corresponding connection setup request message may have a resourceretention rule field for expressing the resource retention rule (orpreference) for that connection. Table 23 shows an exemplary format of aconnection setup request message that allows specifying in the resourceretention rule field a connection to be excluded from a slavedconnection termination. The value of the resource retention rule fieldmay be a boolean value, specifying ‘retain’ or ‘not to retain.’ Theaction for the power mode may be determined by the default behavior orby an action field delivered in the same connection request message orin a subsequent connection change message.

TABLE 23 Connection setup request message (Requesting Retaining Rule forthe Idle mode) DST SRC CMD Classifier Normal Sleep mode Resource modeaction action retention rule

As an alternative to the resource retention rule field, the connectionsetup request may have an action field for a power mode. The presence ofan action field for the power mode is interpreted as an implicit requestfor resource retention for the action. The format for a connection setuprequest message that has an idle mode action field is already shown inTable 14 above.

If a power mode is associated with a slaved activation or deactivationof a connection (i.e., activation or deactivation of a connection istriggered by a specified event, such as a power mode transition), aterminal or a network edge point may request a specified connection tobe excluded from the slaved connection activation or deactivation. Theconnection setup request message may thus include a field or fields forrequesting the exclusion of the connection from the slaved activation,deactivation, or both. For example, when a terminal transits from anormal mode to an idle mode, all connections associated with theterminal may be terminated to release the resources.

Exclusion from a slaved operation (termination, activation, ordeactivation) may be requested whenever a connection setup requestmessage is exchanged. Connections may be excluded one by one or all atonce (i.e., by a single omnibus request) at the time when the terminalis coupled to a network edge point, or when a power mode transitionmessages are exchanged. For example, when a power mode transitionmessage is used as a single request for all connections to be excludedfrom the slaved connection termination, the resource retention field ofthe transition message may have the value of “N”, as shown in Table 6above.

Alternatively, service rules need not be specified one connection at atime. Instead, service rules for more than one connection can bedelivered in a single message that incorporates multiple CMDs with otheraccompanying relevant fields. Table 24 shows an exemplary message whichincludes two CMDs, each being accompanied by a classifier (CSF) field, anormal mode action (NMA) field, a sleep mode action (SMA) field, and anidle mode action (IMA) field.

TABLE 24 Delivery of Service Rules for Multiple Connections DST SRC CMD1 CSF 1 NMA 1 SMA 1 IMA 1 CMD 2 CSF 2 NMA 2 SMA 2 IMA2

When there the same CMD is specified for more than one connection,efficiency may be achieved by specifying only a single CMD. Theaccompanying fields for each connection may nevertheless have to bespecified. TABLE 25 illustrates an exemplary message for deliveringservice rules for two connections under the same CMD. In Table 25, thefields for each connection appear as in a group (“connection orientedlist”). For example, CMD 1, CSF 1, NMA 1, SMA 1 and IMA 1 are fieldspertaining to connection 1, and are thus grouped together.

TABLE 25 Delivery of Service Rules for Multiple Connections having acommon CMD DST SRC CMD CSF 1 NMA 1 SMA 1 IMA 1 CSF 2 NMA 2 SMA 2 IMA 2

Further, when more than one connection specifies the same service rules,the common service rules need being specified in the message only once.In this case, the fields in the message can be arranged such thatconnections specifying the same service rules may be listed togetherwith the associated service rules (“service rule oriented list”). TABLE26 shows a connection-oriented list format for the message where thesame service rules are used for the sleep mode in two connections.

TABLE 26 Delivery of Service Rules for Multiple Connections having acommon Service Rule DST SRC CMD CSF 1 NMA 1 SMA 1 IMA 1 CSF 2 NMA 2 SMA1 IMA 2

Alternatively, a service rule oriented list may be used, where the sleepmode service rules is specified only once next to classifiers CSF1 andCSF2, as shown in TABLE 27.

TABLE 27 Delivery of Service Rules of Table 25, using a Service RuleOriented List DST SRC CMD NMA 1 CSF 1 NMA 2 CSF 2 SMA 1 CSF 1 CSF 2 IMA1 CSF 1 IMA 2 CSF 2

Service rule oriented list may be more efficient than connectionoriented list when the overhead costs associated with listing servicerules are greater than the overhead costs associated with listingconnections. The overhead costs of listing service rules grow when thenumber of bits required to express a service rule becomes large, andwhen the same service rules are repeated. TABLE 26 and TABLE 27 showthat, in a service rule oriented list, even though the service rule(SMA1) appears only once, the number of appearances of the connectionspecifiers (i.e., CSF 1 and CSF 2) grow from 2 to 6.

The number of bits required to express each connection or service ruleshould be examined. If a connection ID (CID), or another identifier,indicator, designator, or pointer can express the classifier associatedwith a connection using less bits, such a device should be used in themessages, rather than expressly providing the classifier. In someinstances, service rule oriented list are more efficient. Similarly, ifa service rule ID or any other identifier, indicator, designator, orpointer can express the service rule with less bits, such a deviceshould be used in the messages, rather than directly stating servicerule. The service rule can sometimes be described by a Boolean variable(e.g., “to alert” or “not to alert”, “to discard” or “not to discard”,and “to retain resource or not to retain resource”) to enhanceefficiency.

When the number of service rules is very small (e.g., two, in the caseof a Boolean service rule), and when all the connections are known, aservice rule oriented list may be used in which one service rule isspecified implicitly. In this case, all the connections that are notexpressly listed are assumed to be covered by the implicit service rule.Where the number of connections is large, much savings in overhead maybe realized. For example, if service rules SMA 1 and SMA 2 for the sleepmode are the only service rules that need to be described, and there aresix (6) connections (CSF1 to 6), TABLE 29 shows a message using aservice rule oriented list in which SMA 1 is the sleep mode service rulefor CSF 1, CSF2, and CSFs 4 to 6, while SMA 2 is the service rule forCSF 3.

TABLE 29 Delivery of service rules (service rule oriented list) DST  SRCCMD  SMA 1 CSF 1  CSF 2 CSF 4  CSF 5 CSF 6  SMA 2 CSF 3 

Alternatively, one need only provide a service rule oriented list forservice list SMA 2 of connection CSF 2, and allowing all the unlistedconnections (i.e., CSF1, CSF2, and CSFs 4 to 6) to be implicitlyassociated service rule SMA 2, as shown in Table 30.

TABLE 30 Delivery of service rules (service rule oriented list withimplicit association) DST SRC CMD SMA 2 CSF 3

If there is a default Boolean service rule (e.g., service rule SMA1)which is not expressly listed in a message, the service rule field in amessage of Table 30 may also be omitted, as it is clear that thespecified connection uses service rule SMA 2.

TABLE 31 Delivery of service rules (service rule oriented list withimplicit association) DST SRC CMD CSF 3

In some instances, adopting a default service rule, allowing implicitassociation with a service list may also cause inefficiency. TABLE 32illustrates a case when the default service rule is SMA2, so thatconnections using service rule SMA1 have to be included in the message:

TABLE 32 Delivery of service rules (service rules oriented list withimplicit association) DST SRC CMD CSF 1 CSF 2 CSF 4 CSF 5 CSF 6

Thus, a service rule field in a message may enable flexible listing,where one can choose the list with a lesser overhead to be used (e.g.,the message of in TABLE 30). Also, when there are more than two servicerule options, a service rule field may not be omitted, even when thereis a default service rule, since the two or more connection lists cannotbe distinguished without a service rule field.

Alternatively, a terminal and network edge point may opt to omit thelist for a service rule when there is no connection using the servicerule. In this case, a service rule oriented list is provided for eachservice rule associated with a connection. This approach allows adifferential listing method to be used, as explained below.

Terminal and network edge point may opt to send a message only whenthere is a change in the service oriented or connection oriented list.The list that provides only the change is termed a “differentiallisting”. If there is a service rule oriented list for SMA1, forexample, then the connections in the list can be interpreted as changingthe service rule to SMA1 from some other service rule or noneassociated. TABLE 33 illustrates the case when the connection of CSF3 ischanging to service rule SMA1 from service rule SMA2, and the connectionof CSF 1 is changed from a service rule SMA 1 to SMA 2.

TABLE 33 Delivery of service rules (differential listing) DST SRC CMDSMA 1 CSF 3 SMA 2 CSF 1

In differential listing, a service rule that is not associated with alist is interpreted as representing a service rule that is notassociated with a connection.

The initial state in differential listing may be first defined using aconnection-oriented list, predetermined default values, a method ofservice rule oriented listing, or any other method that defines theinitial service rule. Service rules may also be specified in conjunctionwith exchange of power mode transition messages, control messages,management messages, or data messages.

After a connection is set up, both the terminal and the network edgepoint may change the parameters of the connection, including anyclassification rule or action. In one embodiment, only theclassification rule and the action for the normal mode are defined atthe connection setup procedure, and the actions for the sleep and idlemodes may be defined later by one or more connection change procedures.

To achieve a connection change, as provided in Table 4 above, theconnection management messages include a connection change requestmessage, a connection change response message, and a connection changeACK message. The formats for the connection change request, theconnection change response, and the connection change ACK messages aresimilar to those discussed above for the connection setup request, theconnection setup response, and the connection setup ACK messages. Aconnection ID may be included in each connection change request message.

To terminate a connection, a connection close request message is sent,and a connection close response message confirms the close request.Tables 34 and 35 provide exemplary formats for the connection closerequest and the connection close response messages, respectively.

TABLE 34 Connection close request message DST SRC CMD Connection ID

TABLE 35 Connection close response message DST SRC CMD Connection ID

A slaved connection termination can be achieved without exchange of anyconnection termination messages. A connection may be activatedimmediately after the connection set up or connection change procedureis carried out. However, a connection may be activated separately fromthe connection set up or connection change procedure. When a connectionis set up but is not activated, the resource for the connection may bereserved or provisioned in the QoS mechanism, before the QoS mechanismoperates communication in the connection. If activation is separated,additional messages such as connection activation request or connectionactivation response messages are exchanged.

A connection may be deactivated without closing the connection. When aconnection is deactivated but not closed, the resource for theconnection may still be reserved or provisioned in the QoS mechanism,even though the QoS mechanism is not operating on the connection. Ifdeactivation is separated from connection closing, additional messagessuch as connection deactivation request or connection deactivationresponse messages are exchanged.

In one embodiment, when a terminal enters normal mode, all connectionsassociated with the service for the normal mode are activated.Similarly, when a terminal transitions into a sleep mode, allconnections associated with services in the sleep mode are reactivated(deactivated and activated). In that embodiment, per connectionactivation or deactivation messages are not used; only the power modetransition messages, such as sleep mode request and sleep mode responsemessages are exchanged to trigger the activation.

A connection may be set up by an internal or external provisioningserver, which executes a service rule or an alerting rule as a domainadministrator, a service provider, or a network edge pointadministrator. FIG. 6 shows a provisioning process, in accordance withone embodiment of the present invention. As shown in FIG. 6, at step602, a provision manager of the network edge point (e.g., provisionmanager 405) may communicate with a provisioning server (e.g.,provisional server 601) to receive the service or alerting rules. Theprovisioning server then cooperates with the connection manager and thepower mode manager of a terminal (steps 603 and 604) to set up one ormore connections accordingly. As shown in FIG. 6, for provisioning, aprovision request message, a provision response message, and a provisionACK message may be exchanged between a provisional server 601 and aprovisioning manager 405 of a network edge point. The formats of thesemessages may be similar to those of connection setup request, connectionsetup response, and connection setup ACK messages already describedabove.

When a mobile terminal changes its point of network attachment from onenetwork edge point another, some connections are preferably kept alive.A handoff manager of a terminal (e.g., handoff manager 503) typicallymanages the handoff-related operations. A handoff manager of a networkedge point (e.g., handoff manager 406) communicates with the handoffmanager of an associated terminal to assist or lead the handoffprocesses, including the transfer of connections, where necessary, so asto avoid service disruption and over-the-air signaling during handoff.In a transfer of connections, a connection transfer request message, aconnection transfer response message, and a connection transfer ACKmessage are exchanged, as provided in Table 4 above. The formats of theconnection transfer request, the connection transfer response, and theconnection transfer ACK messages can be similar to those of theconnection setup request, the connection setup response, and theconnection setup ACK messages. The handoff messages may includeinformation regarding the connections to be transferred, such as therelevant parts of a service table.

The term ‘service’ refers to any operation performed on a classifiedpacket. Delivering and discarding a packet are examples of services.Delivering a particular level of QoS for packets in a connection isanother example of a service. A service manager in a network edge point(e.g., service manager 404) may direct classified packets into a QoSmechanism or a dropper, according to the service table, based on thepacket classification and the receiver's power mode. In someembodiments, the service manager communicates with a connection managerto access a service table whenever it processes a packet. Alternatively,the service manager may maintain its own service table, as shown in theexample in Table 11, and may communicate with a communication managerwhenever an update to the table is required. As another alternative, aservice manager may maintain a service rule table such as that shown inTable 36, and may communicate with communication manager when there isany change in the table. In Table 36, unlike Table 11 above, packets areprovided to the service manager with a connection ID that enables theservice manager to match the packet to a service without executing aclassification step.

TABLE 36 Service rule table Connection ID Receiver ID Power statusAction 1 1 Normal QoS spec 1 Sleep QoS spec 2 Idle Discard 2 1 NormalQos spec 3 Sleep Discard Idle Discard . . . . . . . . . . . . I 2 NormalQos spec j Sleep Qos spec j + 1 Idle Discard i + 1 1 Normal QoS spec 1Sleep Discard Idle Discard 2 Normal QoS spec 1 Sleep QoS spec 2 IdleDiscard . . . . . . . . . N Normal Discard Sleep Discard Idle Discard .. . . . . . . . . . . M N Normal QoS spec 1 Sleep QoS spec 2 Idle QoSspec 4

A service manager (e.g., service manager 404) may also communicate witha power mode manager (e.g., power mode manager 403) to access a terminalpower status table (e.g., the terminal power status table shown in Table10). Alternatively, a service manager may maintain its own terminalpower mode table. QoS may be defined by a QoS specification, whichspecifies such parameters as traffic, service type, service class,service priority, and per hop behavior. For example, a QoS specificationmay include a maximum sustained traffic rate, a maximum traffic burstrate, a minimum reserved traffic rate, a minimum tolerable traffic rate,a scheduling type, a bandwidth request or transmission policy, atolerated jitter, or a maximum latency. As another example, a QoSspecification may include an access policy, a user priority, an ACKpolicy, a schedule, a nominal packet size, a maximum packet size, aminimum service interval, a maximum service interval, an inactivityinterval, a suspension interval, a service start time, a minimum datarate, a mean data rate, a peak data rate, a maximum burst size, a delaybound, a minimum physical rate, a surplus bandwidth allowance, or amedium time.

QoS mechanism may include a scheduler, a poller, a policer, a shaper, abuffer, a bandwidth allocation unit, a resource reservation unit, oranother suitable means for delivering a particular QoS to the packet.When a packet is received, a QoS mechanism first finds the QoSspecification associated with the packet, and may access a service tableor service rule table, which may be maintained by the QoS mechanism.Alternatively, a service table may be accessed through a connectionmanager or a service manager. A packet may be received with a connectionID (CID). A QoS mechanism may also communicate with a power mode managerto access a terminal power mode table, such as that shown in Table 10.Alternatively, a QoS mechanism may maintain its own terminal power modetable. A QoS mechanism may configure or provision itself to operateaccording to a QoS specification.

A broadcast or multicast packet may have multiple receiving terminals indifferent power modes, with different service rules. Therefore, thepresent invention allows multicast or broadcast packets to be deliveredto each terminal, or be discarded, according to packet classificationand each terminal's power modes. Further, the present invention allows areceiver in a power-saving mode to be alerted according to packetclassification and the power-saving modes of the multiple receivers.

In one embodiment, a terminal maintains a service table which defines aclassification rule, a service rule, and an alerting rule for all itsconnections, including broadcast or multicast packets. This servicetable (e.g., the service table shown in Table 13) may be managed by theterminal's connection manager (e.g., connection manager 501). A networkedge point receives the service tables of all terminals it communicateswith through connection set up or connection change procedures, and mayintegrate all these service tables into its own service table (e.g.,service table shown in Table 11). An example of a service rule involvinga broadcast connection is provided in the entry corresponding toconnection ID ‘i+1’ classification rule Table 12, service rule Table 36,and alerting rule Table 9.

According to one embodiment of the present invention, a broadcast ormulticast packet is delivered with a QoS at least at the level specifiedfor that service in the service table. As a result, a broadcast ormulticast packet is discarded only when all receivers requiresdiscarding the packet. Each receiving terminal of a broadcast ormulticast packet is alerted, if alerting is specified for that terminal.As shown in the example of Table 12, the packets for the broadcastconnection with connection ID ‘i+1’ are sent to all terminals 1 to N. Alist of all receivers of a multicast connection may be maintained by aconnection manager (e.g., connection manager 402).

To illustrate, consider terminals 1, 2, and N as having normal, sleep,and idle power modes, respectively. Table 36 shows, for the respectivepower modes of the receiving terminals 1, 2 and N, the services to berendered are QoS spec 1, QoS spec 2, and ‘discard’. If QoS spec 1 is ahigher level of service than QoS spec 2, a broadcast packet is deliveredonly once to terminal 1 with QoS spec 1. For terminal 2, however, thepacket may be delivered twice: once with QoS spec 1 unsuccessfully, asterminal 2 is in a sleep mode when the delivery is first attempted.Delivery will be successful under QoS 2, which specifies alertingterminal 2 in the alerting rule table (Table 9).

Consider next that the power modes of terminals 1, 2, and N are in idle,idle, and sleep power modes, respectively. As shown in Table 36, theservices corresponding to the respective power modes of these receivingterminals are all ‘discard’. Further, as none of the terminals specifyan alert, none of these terminals are alerted.

FIG. 7 shows a handoff procedure by which a terminal detaches from onenetwork edge point and attaches to another. As a part of a connectiontransfer, the service table of the network edge point 1 that is relevantto the terminal is transferred to the network edge point 2 forintegration into the service table of the network edge point 2. FIG. 7shows that the connection to be transferred may be one that isestablished between provisioning server 601, network edge point 1 andterminal 500 through provisioning procedure 602 and connection set upprocedure 603 discussed above in conjunction with FIG. 6. At some pointin time, terminal 500 initiates handoff procedure 701 with network edgepoint 1 or network point 2, or both. Connection transfer is effectuatedbetween network edge points 1 and 2. A connection transfer according tothe present invention avoids disruption in the ongoing connectionsduring handoff, and also helps avoid the over-the-air signaling that maybe required for closing connection with the network edge point 1 and forsetting up connection with the network edge point 2.

The detailed description above is provided to illustrate the specificembodiments of the present invention and is not intended to be limiting.Numerous variations and modifications within the scope of the presentinvention are possible. The present invention is set forth in theaccompanying claims.

We claim:
 1. A network edge point operable to be associated with aterminal in a communication network associated with a terminal andreceiving to receive packets from the network that specify the terminalas destination, the network edge point comprising: a connection managerfor determining a classification rule for the packets; a classifier thatassigns for assigning to each packet a classification according to theclassification rule; and a service manager that maps for mapping aservice to the packet according to the packet's classification and acurrent power mode associated with the terminal, wherein the servicemanager accesses is for accessing a rule table to determine whether theterminal should be alerted from a power saving state to process thepacket.
 2. A network edge point as in claim 1, wherein the classifierassigns is for assigning a connection identification to the packet.
 3. Anetwork edge point as in claim 1, wherein the service mapping isdetermined based on a functionality of the packet and the current powermode.
 4. A network edge point as in claim 3, wherein the rule table isfor being accessed using the packet's classification and the currentpower mode associated with the terminal.
 5. A network edge point as inclaim 4, wherein the terminal provides is for providing the rule tableto the network edge point.
 6. A network edge point as in claim 1,wherein the terminal provides the current power mode to the network edgepoint when the terminal undertakes a power mode transition.
 7. A networkedge point as in claim 1, wherein the connection manager manages is formanaging the connection between the network edge point and the terminal.8. A network edge point as in claim 1, further comprising a hand-offmanager, which transfers for transferring the connection from thenetwork edge point to a second network edge point.
 9. A network edgepoint as in claim 8, wherein a portion of the service mapping associatedwith the terminal is transferred to the second network edge point at thetransfer of the connection to the second network edge point.
 10. Anetwork edge point as in claim 1 wherein, when the packet specifiesmultiple recipients, each recipient receives at least the least of theservices specified for the multiple recipients.
 11. A network edge pointas in claim 1, wherein the mapped service comprises alerting theterminal.
 12. A network edge point as in claim 1, wherein the mappedservice comprises not alerting the terminal.
 13. A network edge pointoperable to be associated with a terminal in a communication networkassociated with a terminal and receiving to receive packets from thenetwork that specify the terminal as destination, the network edge pointcomprising: a connection manager for determining a classification rulefor the packets; a classifier that assigns for assigning to each packeta classification according to the classification rule; and a servicemanager that maps for mapping a service to the packet according to thepacket's classification and a current power mode associated with theterminal, wherein the service manager accesses is for accessing acurrent power mode table to determine the current power mode of theterminal.
 14. A method for providing service in a network edge point ina computer communication network having a connection with a terminal,the method comprising: classifying packets received from thecommunication network that specify the terminal as destination andassigning to each packet a classification; determining a service for thepacket according to the packet's classification and a current power modeassociated with the terminal; accessing a rule table to determinewhether or not the terminal should be alerted from the current powermode to process the packet; and accordingly providing the service.
 15. Amethod as in claim 14, wherein classifying packets comprises assigning aconnection identification to each packet.
 16. A method as in claim 14,wherein the service is determined based on a functionality of the packetand the current power mode.
 17. A method as in claim 16, wherein therule table is accessed using the packet's classification and the currentpower mode associated with the terminal.
 18. A method as in claim 17,wherein the terminal provides the rule table to the network edge point.19. A method as in claim 14, further comprising notifying the networkedge point the terminal's current power mode, when the terminalundertakes a power mode transition.
 20. A method as in claim 14, furthercomprising managing the connection with the terminal in a connectiontable.
 21. A method as in claim 14, further comprising following ahand-off procedure when the terminal transfers the connection from thenetwork edge point to a second network edge point.
 22. A method as inclaim 21, wherein a portion of a service table associated with theterminal is transferred to the second network edge point at the transferof the connection to the second network edge point.
 23. A method as inclaim 14 wherein, when the packet specifies multiple recipients, eachrecipient receives at least the least of the services specified for themultiple recipients.
 24. A method as in claim 14; wherein the determinedservice comprises alerting the terminal.
 25. A method as in claim 14,wherein the determined service comprises not alerting the terminal. 26.A method as in claim 14 wherein, when the packet specifies multiplerecipients, each recipient receives at least the least of the servicesspecified for the multiple recipients.
 27. A method for providingservice in a network edge point in a computer communication networkhaving a connection with a terminal, the method comprising: classifyingpackets received from the communication network that specify theterminal as destination and assigning to each packet a classification;determining a service for the packet according to the packet'sclassification and a current power mode associated with the terminal,wherein a current power mode table is accessed to determine the currentpower mode of the terminal; and providing the service.
 28. A networkedge point operable to be associated with a terminal in a communicationnetwork associated with a terminal and receiving to receive packets fromthe network that specify the terminal as destination, the network edgepoint comprising: a connection manager for determining a classificationrule for the packets; a classifier that assigns for assigning to eachpacket a classification according to the classification rule; and aservice manager that maps for mapping a service to the packet accordingto the packet's classification and a current power mode associated withthe terminal, wherein the service is mapped according to a service tablecomprising quality of service (QoS) specifications.
 29. A network edgepoint operable to be associated with a terminal in a communicationnetwork associated with a terminal and receiving to receive packets fromthe network that specify the terminal as destination, the network edgepoint comprising: a connection manager for determining a classificationrule for the packets; a classifier that assigns for assigning to eachpacket a classification according to the classification rule; and aservice manager that maps for mapping a service to the packet accordingto the packet's classification and a current power mode associated withthe terminal, wherein the terminal provides is for providing the networkedge point mapping between the service and the packet as a function ofpacket classification and the terminal's power mode.
 30. A network edgepoint operable to be associated with a terminal in a communicationnetwork associated with a terminal and receiving to receive packets fromthe network that specify the terminal as destination, the network edgepoint comprising: a connection manager for determining a classificationrule for the packets; a classifier that assigns for assigning to eachpacket a classification according to the classification rule; and aservice manager that maps for mapping a service to the packet accordingto the packet's classification and a current power mode associated withthe terminal, wherein the mapped service comprises discarding thepacket, and, wherein a criterion for determining whether or not todiscard the packet is based on packet classification and the terminal'spower mode.
 31. A network edge point as in claim 30, wherein theterminal provides is for providing the criterion to the network edgepoint.
 32. A network edge point operable to be associated with aterminal in a communication network associated with a terminal andreceiving to receive packets from the network that specify the terminalas destination, the network edge point comprising: a connection managerfor determining a classification rule for the packets; a classifier thatassigns for assigning to each packet a classification according to theclassification rule; and a service manager that maps for mapping aservice to the packet according to the packet's classification and acurrent power mode associated with the terminal, wherein the servicemanager is for further determines determining whether or not a serviceresource is maintained for the packet according to a criterion thatdepends on the packet's classification and the current power modeassociated with the terminal.
 33. A network edge point as in claim 32,wherein the terminal provides is for providing the criterion to thenetwork edge point.
 34. A method for providing service in a network edgepoint in a computer communication network having a connection with aterminal, the method comprising: classifying packets received from thecommunication network that specify the terminal as destination andassigning to each packet a classification; determining a service for thepacket according to the packet's classification and a current power modeassociated with the terminal, wherein a service table provided by theterminal to the network edge point provides quality of service (QoS)specifications; and providing the service.
 35. A method as in claim 34,wherein the service is determined based on a functionality of the packetand the current power mode.
 36. A method for providing service in anetwork edge point in a computer communication network having aconnection with a terminal, the method comprising: classifying packetsreceived from the communication network that specify the terminal asdestination and assigning to each packet a classification; determining aservice for the packet according to the packet's classification and acurrent power mode associated with the terminal, wherein the servicecomprises discarding the packet and wherein a criterion for determiningwhether or not to discard the packet is based on packet classificationand the terminal's power mode; and providing the service.
 37. A methodas in claim 36, wherein the terminal provides the criterion to thenetwork edge point.
 38. A method for providing service in a network edgepoint in a computer communication network having a connection with aterminal, the method comprising: classifying packets received from thecommunication network that specify the terminal as destination andassigning to each packet a classification; determining a service for thepacket according to the packet's classification and a current power modeassociated with the terminal, further comprising determining whether ornot a service resource is maintained for the packet according to acriterion that depends on the packet's classification and the currentpower mode associated with the terminal.
 39. A method as in claim 38,wherein the terminal provides the criterion to the network edge point.40. A terminal operable to be associated with a network edge point in acommunication network, the terminal comprising: a power mode manager fordetermining a power mode of the terminal and communicating the powermode to the network edge point; and a connection manager forcommunicating with the network edge point a classification rule forpackets designating the terminal as destination and a service rule,wherein the service rule maps a service to each packet according to thepacket's classification and the power mode of the terminal, wherein theconnection manager provides is for providing a rule table to a servicemanager at the network edge point for determining whether or not theterminal is to be alerted from a power saving state, according to thepacket's classification and the current power mode associated with theterminal.
 41. A terminal as in claim 40, wherein the mapped servicecomprises alerting the terminal.
 42. A terminal as in claim 40, whereinthe mapped service comprises not alerting the terminal.
 43. A terminalas in claim 40, wherein the terminal provides the current power mode tothe network edge point when the terminal undertakes a power modetransition.
 44. A terminal as in claim 40, wherein the connectionmanager manages the connection between the network edge point and theterminal.
 45. A terminal as in claim 40, further comprising a hand-offmanager, which manages for managing the transfer of the terminal'sassociation from the network edge point to a second network edge point.46. A terminal as in claim 45, wherein a portion of the service mappingassociated with the terminal is transferred to the second network edgepoint at the transfer of the connection to the second network edgepoint.
 47. A terminal as in claim 40, wherein whether or not theterminal is to be alerted is determined based on a functionality of thepacket and the current power mode.
 48. A terminal operable to beassociated with a network edge point in a communication network, theterminal comprising: a power mode manager for determining a power modeof the terminal and communicating the power mode to the network edgepoint; and a connection manager for communicating with the network edgepoint a classification rule for packets designating the terminal asdestination and a service rule, wherein the service rule maps a serviceto each packet according to the packet's classification and the powermode of the terminal, wherein the mapped service comprises discardingthe packet, and wherein a criterion for determining whether or not todiscard the packet is based on packet classification and the terminal'spower mode.
 49. A terminal as in claim 48, wherein the criterion isbased on a functionality of the packet and the current power mode.
 50. Aterminal as in claim 48, wherein the terminal provides is for providingthe criterion to the network edge point.
 51. A terminal operable to beassociated with a network edge point in a communication network, theterminal comprising: a power mode manager for determining a power modeof the terminal and communicating the power mode to the network edgepoint; and a connection manager for communicating with the network edgepoint a classification rule for packets designating the terminal asdestination and a service rule, wherein the service rule maps a serviceto each packet according to the packet's classification and the powermode of the terminal, wherein the connection manager provides is forproviding to a service manager of the network edge point a criterionthat depends on the packet's classification and the current power modeassociated with the terminal, the criterion enabling the service managerto determine whether or not a service resource is maintained for thepacket.
 52. A terminal operable to be associated with a network edgepoint in a communication network, the terminal comprising: a power modemanager for determining a power mode of the terminal and communicatingthe power mode to the network edge point; and a connection manager forcommunicating with the network edge point a classification rule forpackets designating the terminal as destination and a service rule,wherein the service rule maps a service to each packet according to thepacket's classification and the power mode of the terminal, wherein theconnection manager is for further communicates communicating to thenetwork edge point a resource retention rule that determines whether ornot a service resource for a packet is maintained, according to thepacket's classification and the power mode of the terminal.
 53. Aterminal as in claim 52, wherein the service resource is maintainedduring the power mode of the terminal and the service rule specifiesthat the terminal is to be alerted.
 54. A method for enabling servicefor a terminal associated with a network edge point in a communicationnetwork, the method comprising: determining a power mode of theterminal; and communicating to the network edge point: (a) the powermode; (b) a classification rule for packets designating the terminal asdestination; and (c) a service rule, wherein the service rule maps aservice to each packet according to the packet's classification and thepower mode of the terminal, and wherein a rule table is accessed todetermine whether or not the terminal is to be alerted from a powersaving state, according to the packet's classification and the currentpower mode associated with the terminal.
 55. A method as in claim 54,wherein the mapped service comprises alerting the terminal.
 56. A methodas in claim 54, wherein the mapped service comprises not alerting theterminal.
 57. A method as in claim 54, wherein the terminal provides thecurrent power mode to the network edge point when the terminalundertakes a power mode transition.
 58. A method as in claim 54, furthercomprising managing the association between the network edge point andthe terminal.
 59. A method as in claim 54, further comprising managingthe transfer of the terminal's association from the network edge pointto a second network edge point.
 60. A method as in claim 59, wherein aportion of the service mapping associated with the terminal istransferred to the second network edge point at the transfer of theconnection to the second network edge point.
 61. A method as in claim54, wherein whether or not the terminal is to be alerted is determinedbased on a functionality of the packet and the current power mode.
 62. Amethod for enabling service for a terminal associated with a networkedge point in a communication network, the method comprising;:determining a power mode of the terminal; and communicating to thenetwork edge point: (a) the power mode; (b) a classification rule forpackets designating the terminal as destination; and (c) a service rule,wherein the service rule maps a service to each packet according to thepacket's classification and the power mode of the terminal, wherein themapped service comprises discarding the packet, and wherein a criterionfor determining whether or not to discard the packet is based on packetclassification and the terminal's power mode.
 63. A method as in claim62, wherein the criterion is based on a functionality of the packet andthe current power mode.
 64. A method as in claim 62, wherein theterminal provides the criterion to the network edge point.
 65. A methodfor enabling service for a terminal associated with a network edge pointin a communication network, the method comprising: determining a powermode of the terminal; and communicating to the network edge point: (a)the power mode; (b) a classification rule for packets designating theterminal as destination; and (c) a service rule, wherein the servicerule maps a service to each packet according to the packet'sclassification and the power mode of the terminal and wherein a servicemanager of the network edge point is provided a criterion that dependson the packet's classification and the current power mode associatedwith the terminal, the criterion enabling the service manager todetermine whether or not a service resource is maintained for thepacket.
 66. A method for enabling service for a terminal associated witha network edge point in a communication network, the method comprising:determining a power mode of the terminal; and communicating to thenetwork edge point: (a) the power mode; (b) a classification rule forpackets designating the terminal as destination; and (c) a service rule,wherein the service rule maps a service to each packet according to thepacket's classification and the power mode of the terminal and whereinthe network edge point is provided a resource retention rule thatdetermines whether or not a service resource for a packet is maintained,according to the packet's classification and the power mode of theterminal.
 67. A method as in claim 66, wherein the service resource ismaintained during the power mode of the terminal and the service rulespecifies that the terminal is to be alerted.
 68. A network edge pointoperable to be associated with a terminal in a communication network andto receive from the network packets specifying the terminal asdestination, the network edge point comprising: a connection manager forselecting a classification rule for the packets; a classifier forassigning to each packet a classification according to theclassification rule; and a service manager for applying a service rulethat corresponds to the packet's classification and a current power modeof the terminal, wherein applying the service rule results in eitherdelivering or discarding the packet.
 69. A network edge point as inclaim 67, wherein the service rule is provided by the terminal.
 70. Anetwork edge point as in claim 69, wherein the terminal provides theservice rule when the terminal establishes or changes a connectionbetween the network edge point and the terminal.
 71. A network edgepoint as in claim 69, wherein the service rule defines one or more of adefault service rule, a default classification, and a default powermode.
 72. A network edge point as in claim 68, wherein the terminalprovides the current power mode to the network edge point when theterminal undertakes a power mode transition.
 73. A network edge point asin claim 72, wherein the service rule is provided by the terminal at thetime the terminal provides the current power mode to the network edgepoint.
 74. A network edge point as in claim 68, wherein the service ruleis provided by a provisioning server.
 75. A network edge point as inclaim 74, wherein the provisioning server provides the service rule atthe time the provisioning server establishes or changes a connectionbetween the network edge point and the terminal.
 76. A network edgepoint as in claim 75, wherein the service rule defines one or more of adefault service rule, a default classification, and a default powermode.
 77. A network edge point as in claim 68, wherein the service ruleis provided by a second network edge point with which the terminal isassociated prior to associating with the current network edge point. 78.A network edge point as in claim 68, wherein, when the packet specifiesmultiple recipients, the packet is discarded only when the service ruleinstructs discarding the packet for all recipients.
 79. A network edgepoint as in claim 68, wherein, when the service rule specifiesdelivering the packet, the service rule further specifies a quality ofservice.
 80. A network edge point as in claim 68, wherein the servicemanager is for further selecting an alerting rule that is associatedwith the packet's classification and the current power mode of theterminal, wherein the alerting rule specifies whether or not to alertthe terminal.
 81. A network edge point as in claim 80, wherein thealerting rule specifies alerting the terminal when the service rulerequires delivering the packet, and not alerting the terminal when theservice rule requires discarding the packet to be discarded.
 82. Anetwork edge point operable to be associated with a terminal in acommunication network and to receive from the network packets specifyingthe terminal as destination, the network edge point comprising: aconnection manager for selecting a classification rule for the packets;a classifier for assigning to each packet a classification according tothe classification rule; and a service manager for applying an alertingrule that corresponds to the packet's classification and a current powermode of the terminal, the alerting rule specifying whether or not toalert the terminal, wherein, while in the current power mode, theterminal relies on receiving the alert to be informed of the packetdestined to the terminal.
 83. A network edge point as in claim 82,wherein the alerting rule is provided by the terminal.
 84. A networkedge point as in claim 83, wherein the terminal provides the alertingrule at the time the terminal establishes or changes a connectionbetween the network edge point and the terminal.
 85. A network edgepoint as in claim 82, wherein the alerting rule defines one or more of adefault alerting rule, a default classification, and a default powermode.
 86. A network edge point as in claim 82, wherein the terminalprovides the current power mode to the network edge point at the timethe terminal undertakes a power mode transition.
 87. A network edgepoint as in claim 86, wherein the alerting rule is provided by theterminal at the time the terminal provides the current power mode to thenetwork edge point.
 88. A network edge point as in claim 82, wherein thealerting rule is provided by a provisioning server.
 89. A network edgepoint as in claim 88, wherein the provisioning server provides thealerting rule at the time the provisioning server establishes or changesa connection between the network edge point and the terminal.
 90. Anetwork edge point as in claim 88, wherein the alerting rule defines oneor more of a default alerting rule, a default classification, and adefault power mode.
 91. A network edge point as in claim 82, wherein thealerting rule is provided by a second network edge point with which theterminal is associated prior to associating with the current networkedge point.
 92. A network edge point as in claim 82, wherein when thealerting rule specifies alerting the terminal, an alerting message istransmitted from the network edge point.
 93. A network edge point as inclaim 92 wherein the alerting message further comprises a request to theterminal for performing a specified operation.
 94. A network edge pointas in claim 82, wherein, the terminal is alerted only when, at thenetwork edge point, there is at least a packet that specifies theterminal as destination and that satisfies at least one alerting rule'srequirement for alerting the terminal.
 95. In a network edge point in acommunication network that is currently associated with a terminal andthat receives from the network packets specifying the terminal asdestination, a method comprising: selecting a classification rule forthe packets; assigning to each packet a classification according to theclassification rule; and applying a service rule that corresponds to thepacket's classification and a current power mode associated with theterminal, wherein applying the service rule results in either deliveringor discarding the packet.
 96. A method as in claim 95, wherein theservice rule is provided by the terminal.
 97. A method as in claim 96,wherein the terminal provides the service rule when the terminalestablishes or changes a connection between the network edge point andthe terminal.
 98. A method as in claim 96, wherein the service ruledefines one or more of a default service rule, a default classification,and a default power mode.
 99. A method as in claim 95, wherein theterminal provides the current power mode to the network edge point whenthe terminal undertakes a power mode transition.
 100. A method as inclaim 99, wherein the service rule is provided by the terminal at thetime the terminal provides the current power mode to the network edgepoint.
 101. A method as in claim 95, wherein the service rule isprovided by a provisioning server.
 102. A method as in claim 101,wherein the provisioning server provides the service rule at the timethe provisioning server establishes or changes a connection between thenetwork edge point and the terminal.
 103. A method as in claim 102,wherein the service rule defines one or more of a default service rule,a default classification, and a default power mode.
 104. A method as inclaim 95, wherein the service rule is provided by a second network edgepoint with which the terminal is associated prior to associating withthe current network edge point.
 105. A method as in claim 95, wherein,when the packet specifies multiple recipients, the packet is discardedonly when the service rule instructs discarding the packet for allrecipients.
 106. A method as in claim 95, wherein, when the service rulespecifies delivering the packet, the service rule further specifies aquality of service.
 107. A method as in claim 95, further comprisingselecting an alerting rule that is associated with the packet'sclassification and the current power mode of the terminal, wherein thealerting rule specifies whether or not to alert the terminal.
 108. Amethod as in claim 107, wherein the alerting rule specifies alerting theterminal when the service rule requires delivering the packet, and notalerting the terminal when the service rule requires discarding thepacket to be discarded.
 109. In a network edge point in a communicationnetwork that is currently associated with a terminal and that receivesfrom the network packets specifying the terminal as destination, amethod comprising: selecting a classification rule for the packets;assigning to each packet a classification according to theclassification rule; and applying an alerting rule that corresponds tothe packet's classification and a current power mode associated with theterminal, the alerting rule specifying whether or not to alert theterminal, wherein, while in the current power mode, the terminal relieson receiving the alert to be informed of the packet destined to theterminal.
 110. A method as in claim 109, wherein the alerting rule isprovided by the terminal.
 111. A method as in claim 110, wherein theterminal provides the alerting rule at the time the terminal establishesor changes a connection between the network edge point and the terminal.112. A method as in claim 109, wherein the alerting rule defines one ormore of a default alerting rule, a default classification, and a defaultpower mode.
 113. A method as in claim 109, wherein the terminal providesthe current power mode to the network edge point at the time theterminal undertakes a power mode transition.
 114. A method as in claim113, wherein the alerting rule is provided by the terminal at the timethe terminal provides the current power mode to the network edge point.115. A method as in claim 109, wherein the alerting rule is provided bya provisioning server.
 116. A method as in claim 115, wherein theprovisioning server provides the alerting rule at the time theprovisioning server establishes or changes a connection between thenetwork edge point and the terminal.
 117. A method as in claim 115,wherein when the alerting rule defines one or more of a default alertingrule, a default classification, and a default power mode.
 118. A methodas in claim 109, wherein the alerting rule is provided by a secondnetwork edge point with which the terminal is associated prior toassociating with the current network edge point.
 119. A method as inclaim 109, wherein, when the alerting rule specifies alerting theterminal, an alerting message is transmitted from the network edgepoint.
 120. A method as in claim 109, wherein the alerting messagefurther comprises a request to the terminal for performing a specifiedoperation.
 121. A method as in claim 109, wherein, the terminal isalerted only when, at the network edge point, there is at least a packetthat specifies the terminal as destination and that satisfies at leastone alerting rule's requirement for alerting the terminal.
 122. Aterminal operable to be associated with a network edge point in acommunication network and to be a destination of packets transmitted inthe communication network, the terminal comprising: a connection managerfor providing the network edge point a classification rule for assigningto each packet a classification; and a service manager for receivingpackets from the network edge point each according to a service rulethat corresponds to the packet's classification and a current power modeof the terminal, wherein the service rule specifies either delivering ordiscarding the packet.
 123. A terminal as in claim 122, wherein theterminal provides the service rule when the terminal establishes orchanges a connection between the network edge point and the terminal.124. A terminal as in claim 122, wherein the service rule defines one ormore of a default service rule, a default classification, and a defaultpower mode.
 125. A terminal as in claim 122, wherein the terminalprovides the current power mode to the network edge point when theterminal undertakes a power mode transition.
 126. A terminal as in claim125, wherein the service rule is provided by the terminal at the timethe terminal provides the current power mode to the network edge point.127. A terminal as in claim 122, wherein the service rule is provided bya provisioning server.
 128. A terminal as in claim 127, wherein theprovisioning server provides the service rule at the time theprovisioning server establishes or changes a connection between thenetwork edge point and the terminal.
 129. A terminal as in claim 122,wherein the service rule defines one or more of a default service rule,a default classification, and a default power mode.
 130. A terminal asin claim 122, wherein the service rule is provided by a second networkedge point with which the terminal is associated prior to associatingwith the current network edge point.
 131. A terminal as in claim 122,wherein, when the packet specifies multiple recipients, the packet isdiscarded only when the service rule instructs discarding the packet forall recipients.
 132. A terminal as in claim 122, wherein when theservice rule specifies delivering the packet, the service rule furtherspecifies a quality of service.
 133. A terminal as in claim 122, whereinthe service manager is for operating according to an alerting rule thatis associated with the packet's classification and the current powermode of the terminal, wherein the alerting rule specifies whether or notthe terminal is to be alerted.
 134. A terminal as in claim 133, whereinthe alerting rule specifies alerting the terminal when the service rulerequires delivering the packet, and not alerting the terminal when theservice rule requires discarding the packet to be discarded.
 135. Aterminal operable to be associated with a network edge point in acommunication network and to be a destination of packets transmitted inthe network, the terminal comprising: a connection manager for providingto the network edge point a classification rule that assigns to eachpacket a classification; and a service manager for operating accordingto an alerting rule that corresponds to the packet's classification anda current power mode of the terminal, the alerting rule specifyingwhether or not to alert the terminal, wherein, while in the currentpower mode, the terminal relies on receiving the alert to be informed ofthe packet destined to the terminal.
 136. A terminal as in claim 135,wherein the terminal provides the alerting rule at the time the terminalestablishes or changes a connection between the network edge point andthe terminal.
 137. A terminal as in claim 135, wherein the alerting ruledefines one or more of a default alerting rule, a defaultclassification, and a default power mode.
 138. A terminal as in claim135, wherein the terminal provides the current power mode to the networkedge point at the time the terminal undertakes a power mode transition.139. A terminal as in claim 138, wherein the alerting rule is providedby the terminal at the time the terminal provides the current power modeto the network edge point.
 140. A terminal as in claim 135, wherein thealerting rule is provided by a provisioning server.
 141. A terminal asin claim 140, wherein the provisioning server provides the alerting ruleat the time the provisioning server establishes or changes a connectionbetween the network edge point and the terminal.
 142. A terminal as inclaim 135, wherein the alerting rule defines one or more of a defaultalerting rule, a default classification, and a default power mode. 143.A terminal as in claim 135, wherein the alerting rule is provided by asecond network edge point with which the terminal is associated prior toassociating with the current network edge point.
 144. A terminal as inclaim 135, wherein when the alerting rule specifies alerting theterminal, an alerting message is transmitted from the network edgepoint.
 145. A terminal as in claim 144, wherein the alerting messagefurther comprises a request to the terminal for performing a specifiedoperation.
 146. A terminal as in claim 135, wherein, the terminal isalerted only when, at the network edge point, there is at least a packetthat specifies the terminal as destination and that satisfies at leastone alerting rule's requirement for alerting the terminal.
 147. In aterminal in a communication network that is currently associated with anetwork edge point and that is a destination of packets transmitted inthe communication network, a method comprising: providing the networkedge point a classification rule for assigning to each packet aclassification; and receiving packets from the network edge point eachaccording to a service rule that corresponds to the packet'sclassification and a current power mode of the terminal, wherein theservice rule specifies either delivering or discarding the packet. 148.A method as in claim 147, wherein the terminal provides the service rulewhen the terminal establishes or changes a connection between thenetwork edge point and the terminal.
 149. A method as in claim 147,wherein the service rule defines one or more of a default service rule,a default classification, and a default power mode.
 150. A method as inclaim 147, wherein the terminal provides the current power mode to thenetwork edge point when the terminal undertakes a power mode transition.151. A method as in claim 150, wherein the service rule is provided bythe terminal at the time the terminal provides the current power mode tothe network edge point.
 152. A method as in claim 147, wherein theservice rule is provided by a provisioning server.
 153. A method as inclaim 152, wherein the provisioning server provides the service rule atthe time the provisioning server establishes or changes a connectionbetween the network edge point and the terminal.
 154. A method as inclaim 147, wherein the service rule defines one or more of a defaultservice rule, a default classification, and a default power mode.
 155. Amethod as in claim 147, wherein the service rule is provided by a secondnetwork edge point with which the terminal is associated prior toassociating with the current network edge point.
 156. A method as inclaim 147, wherein the packet specifies multiple recipients, the packetis discarded only when the service rule instructs discarding the packetfor all recipients.
 157. A method as in claim 147, wherein the servicerule specifies delivering the packet, the service rule further specifiesa quality of service.
 158. A method as in claim 147, further comprisingoperating according to an alerting rule that is associated with thepacket's classification and the current power mode of the terminal,wherein the alerting rule specifies whether or not the terminal is to bealerted.
 159. A method as in claim 158, wherein the alerting rulespecifies alerting the terminal when the service rule requiresdelivering the packet, and not alerting the terminal when the servicerule requires discarding the packet to be discarded.
 160. In a terminalin a communication network that is currently associated with a networkedge point and that is a destination of packets transmitted in thenetwork, a method comprising: providing to the network edge point aclassification rule that assigns to each packet a classification; andoperating according to an alerting rule that corresponds to the packet'sclassification and a current power mode of the terminal, the alertingrule specifying whether or not to alert the terminal, wherein, while inthe current power mode, the terminal relies on receiving the alert to beinformed of the packet destined to the terminal.
 161. A method as inclaim 160, wherein the terminal provides the alerting rule at the timethe terminal establishes or changes a connection between the networkedge point and the terminal.
 162. A method as in claim 160, wherein thealerting rule defines one or more of a default alerting rule, a defaultclassification, and a default power mode.
 163. A method as in claim 160,wherein the terminal provides the current power mode to the network edgepoint at the time the terminal undertakes a power mode transition. 164.A method as in claim 163, wherein the alerting rule is provided by theterminal at the time the terminal provides the current power mode to thenetwork edge point.
 165. A method as in claim 160, wherein the alertingrule is provided by a provisioning server.
 166. A method as in claim165, wherein the provisioning server provides the alerting rule at thetime the provisioning server establishes or changes a connection betweenthe network edge point and the terminal.
 167. A method as in claim 160,wherein the alerting rule defines one or more of a default alertingrule, a default classification, and a default power mode.
 168. A methodas in claim 160, wherein the alerting rule is provided by a secondnetwork edge point with which the terminal is associated prior toassociating with the current network edge point.
 169. A method as inclaim 168, wherein the alerting rule specifies alerting the terminal, analerting message is transmitted from the network edge point.
 170. Amethod as in claim 169, wherein the alerting message further comprises arequest to the terminal for performing a specified operation.
 171. Amethod as in claim 169, wherein, the terminal is alerted only when, atthe network edge point, there is at least a packet that specifies theterminal as destination and that satisfies at least one alerting rule'srequirement for alerting the terminal.